Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

Test Failure Analysis

Summary: The integration test is timing out after 30s and hitting a 429 (Too Many Requests) rate limit from GitHub's API during teardown.

Root Cause: This failure is unrelated to the PR changes. The PR refactors prompt handler logic (moving task metadata extraction from to ), but the failing test is for GitHub MCP remote integration testing tool calls. The test is hitting GitHub Copilot's MCP endpoint () and encountering:

1. A timeout waiting for a response to the tool call
2. A 429 rate limit error during client disconnection/cleanup

The error occurs at line 630 in client.py during _disconnect() when waiting for the session task to complete, which then raises the 429 error that occurred during the AsyncExitStack cleanup.

Suggested Solution: This is a transient infrastructure issue with the external GitHub API, not a code problem. Options:

1. Retry the workflow - The rate limit should reset after a brief period
2. Add retry logic to the GitHub integration tests with exponential backoff
3. Mock the GitHub API in these tests to avoid hitting real rate limits
4. Increase the integration test timeout beyond 30s to account for rate limiting delays

The PR changes themselves don't affect this code path. The test should pass once GitHub's rate limits reset.

[FAILED] tests/integration_tests/test_github_mcp_remote.py::TestGithubMCPRemote::test_call_tool_ko
Failed: Timeout (>30.0s) from pytest-timeout.

httpx.HTTPStatusError: Client error '429 Too Many Requests' for url 'https://api.githubcopilot.com/mcp/'
For more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/429

async def test_call_tool_ko(
    self, streamable_http_client: Client[StreamableHttpTransport]
):
    """Test calling a non-existing tool"""
    async with streamable_http_client:
        assert streamable_http_client.is_connected()
        with pytest.raises(McpError, match=r"unknown tool|tool not found"):
            await streamable_http_client.call_tool("foo")

Test Failure Analysis

Summary: The integration test test_call_tool_ko is timing out after 30s and hitting a 429 (Too Many Requests) rate limit from GitHub's API during teardown.

Root Cause: This failure is unrelated to the PR changes. The PR refactors prompt handler logic (moving task metadata extraction from low_level.py to server.py), but the failing test is for GitHub MCP remote integration testing tool calls. The test is hitting GitHub Copilot's MCP endpoint (api.githubcopilot.com/mcp/) and encountering:

1. A timeout waiting for a response to the tool call
2. A 429 rate limit error during client disconnection/cleanup

The error occurs at line 630 in client.py during _disconnect() when waiting for the session task to complete, which then raises the 429 error that occurred during the AsyncExitStack cleanup.

Suggested Solution: This is a transient infrastructure issue with the external GitHub API, not a code problem. Options:

1. Retry the workflow - The rate limit should reset after a brief period
2. Add retry logic to the GitHub integration tests with exponential backoff
3. Mock the GitHub API in these tests to avoid hitting real rate limits
4. Increase the integration test timeout beyond 30s to account for rate limiting delays

The PR changes themselves don't affect this code path. The test should pass once GitHub's rate limits reset.

[FAILED] tests/integration_tests/test_github_mcp_remote.py::TestGithubMCPRemote::test_call_tool_ko
Failed: Timeout (>30.0s) from pytest-timeout.

httpx.HTTPStatusError: Client error '429 Too Many Requests' for url 'https://api.githubcopilot.com/mcp/'
For more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/429

async def test_call_tool_ko(
    self, streamable_http_client: Client[StreamableHttpTransport]
):
    """Test calling a non-existing tool"""
    async with streamable_http_client:
        assert streamable_http_client.is_connected()
        with pytest.raises(McpError, match=r"unknown tool|tool not found"):
            await streamable_http_client.call_tool("foo")

Test Failure Analysis

Summary: Two integration tests for GitHub MCP remote are timing out after receiving HTTP 429 (Too Many Requests) errors from the GitHub Copilot API.

Root Cause: The tests test_call_tool_list_commits and test_call_tool_ko are hitting rate limits on the GitHub Copilot API (https://api.githubcopilot.com/mcp/). The tests wait for 30 seconds (the configured timeout) before failing, but the underlying issue is that the API returns a 429 status code indicating the rate limit has been exceeded.

Suggested Solution:

These are external integration tests that depend on third-party API availability and rate limits. Consider one of these approaches:

1. Add retry logic with exponential backoff to the test fixture or client setup for remote API tests
2. Skip or mark as flaky tests that depend on external rate-limited APIs in CI
3. Mock the GitHub Copilot API for these tests instead of making real API calls
4. Add rate limiting handling in the test suite to space out requests to external APIs

The most practical immediate fix would be option 2 - marking these specific tests to be skipped in CI or allowing them to be flaky, since they test integration with an external service that has rate limits outside of our control.

httpx.HTTPStatusError: Client error '429 Too Many Requests' for url 'https://api.githubcopilot.com/mcp/'
For more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/429